Repository navigation
Default RFP proposals to recommended ordering - #1321
nicktytarenko wants to merge 1 commit into
Conversation
The funding feed now accepts ordering=recommended alongside grant_id. When the proposals feed is scoped to one RFP, default to it and offer it in the sort menu. Unscoped feeds keep "best" and never send recommended.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review Summary: ❌ FailedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
|
|
Not needed: the backend now applies the ranking to ordering=best when grant_id is passed (ResearchHub/researchhub-backend#4537). |



What
The Proposals tab on an RFP page now ranks proposals with the backend's new
recommendedordering by default."Recommended" is the first and selected option in that tab's sort menu.
Depends on ResearchHub/researchhub-backend#4537.
How
proposalSortAndFilterConfig.ts: addsrecommendedtoProposalSortOptionand aGRANT_SORT_OPTIONSlist (Recommended + the existing options).FundraiseContext.tsx: when the provider has agrantId, the default sort isrecommendedand the context exposesGRANT_SORT_OPTIONS; otherwise it staysbestwith the existing options. A sort that isn't valid for the current scope falls back to that scope's default, sorecommendedis never sent withoutgrant_id.ProposalSortAndFilters.tsx: renders the options from the context.The main feed's Proposals tab (
/fund/proposals) has nograntIdand is unchanged. The/consciousnesslive proposals list is scoped to its RFP, so it also picks up the recommended order. Nestedgrant.applicationsfrom the grant feed come pre-ranked from the backend and aren't re-sorted on the client.